The current errors should be fixed with #19952 once merged. I only realized later that this blocks the Asciidoctor upgrade.

We should check if we need to tackle spring-io/spring-asciidoctor-extensions#21 before merging this. That issue was opened as a placeholder so it may be that the extensions are already AsciidoctorJ 2.0 compatible.

Is there anything I can help with, @wilkinsona ?

Thanks for the offer, @dreis2211. I think it's been taken care of thanks to @rwinch. I just need to double-check that I didn't break it when merging and then cut a release of the extensions.

The extensions have been released and Boot's now using them. I think we should now be good-to-go on this one.

The PDF generation failed when built locally. I think that's because we're using the configuration property JSON to generate the Asciidoc source. This makes the changes to use, for example, < rather than < have no effect. The < has been replaced with < again by the time the Asciidoctor processing is performed. I think we may need to do some escaping of the description in SingleConfigurationTableEntry instead.

Interesting....I wonder why this didn't fail for me locally? I will take a look again. Sorry for the inconvenience.

Pushed an updated version